SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Using publicly writable directories is security-sensitive

           Security Hotspot
        4. Using clear-text protocols is security-sensitive

           Security Hotspot
        5. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        6. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        7. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        8. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        9. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        10. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        11. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        12. Formatting SQL queries is security-sensitive

           Security Hotspot
        13. Hard-coded credentials are security-sensitive

           Security Hotspot
        14. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Using clear-text protocols is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        Clear-text protocols such as ftp, telnet, or http lack encryption of transported data, as well as the capability to build an authenticated connection. It means that an attacker able to sniff traffic from the network can read, modify, or corrupt the transported content. These protocols are not secure as they expose applications to an extensive range of risks:

        • sensitive data exposure
        • traffic redirected to a malicious endpoint
        • malware-infected software update or installer
        • execution of client-side code
        • corruption of critical information

        Even in the context of isolated networks like offline environments or segmented cloud environments, the insider threat exists. Thus, attacks involving communications being sniffed or tampered with can still happen.

        For example, attackers could successfully compromise prior security layers by:

        • bypassing isolation mechanisms
        • compromising a component of the network
        • getting the credentials of an internal IAM account (either from a service account or an actual person)

        In such cases, encrypting communications would decrease the chances of attackers to successfully leak data or steal credentials from other network components. By layering various security practices (segmentation and encryption, for example), the application will follow the defense-in-depth principle.

        Note that using the http protocol is being deprecated by major web browsers.

        In the past, it has led to the following vulnerabilities:

        • CVE-2019-6169
        • CVE-2019-12327
        • CVE-2019-11065

        Ask Yourself Whether

        • Application data needs to be protected against falsifications or leaks when transiting over the network.
        • Application data transits over an untrusted network.
        • Compliance rules require the service to encrypt data in transit.
        • Your application renders web pages with a relaxed mixed content policy.
        • OS-level protections against clear-text traffic are deactivated.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Make application data transit over a secure, authenticated and encrypted protocol like TLS or SSH. Here are a few alternatives to the most common clear-text protocols:
          • Use ssh as an alternative to telnet.
          • Use sftp, scp, or ftps instead of ftp.
          • Use https instead of http.
          • Use SMTP over SSL/TLS or SMTP with STARTTLS instead of clear-text SMTP.
        • Enable encryption of cloud components communications whenever it is possible.
        • Configure your application to block mixed content when rendering web pages.
        • If available, enforce OS-level deactivation of all clear-text traffic.

        It is recommended to secure all transport channels, even on local networks, as it can take a single non-secure connection to compromise an entire application or system.

        Sensitive Code Example

        import "net/http"
        
        response, err := http.Get("http://www.example.com/") // Sensitive
        
        import "net/smtp"
        
        connection, err := smtp.Dial("mail.example.com:25") // Sensitive
        connection.Hello("my-sending-server.example.com")
        // authenticate and send email
        connection.Quit()
        

        Compliant Solution

        import "net/http"
        
        response, err := http.Get("https://www.example.com/") // Compliant
        
        import (
            "crypto/tls"
            "net/smtp"
        )
        
        tlsConfig := &tls.Config{}
        
        connection, err := smtp.Dial("mail.example.com:25") // Compliant
        connection.Hello("my-sending-server.example.com")
        err = connection.StartTLS(tlsConfig)
        if err == nil {
            // authenticate and send email
        }
        connection.Quit()
        

        Exceptions

        No issue is reported for the following cases because they are not considered sensitive:

        • Insecure protocol scheme followed by loopback addresses like 127.0.0.1 or localhost.

        See

        Documentation

        • AWS Documentation - Listeners for your Application Load Balancers
        • AWS Documentation - Stream Encryption

        Articles & blog posts

        • Google - Moving towards more secure web
        • Mozilla - Deprecating non secure http

        Standards

        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • OWASP - Top 10 2021 Category A2 - Cryptographic Failures
        • CWE - CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
        • CWE - CWE-319 - Cleartext Transmission of Sensitive Information
        • STIG Viewer - Application Security and Development: V-222397 - The application must implement cryptographic mechanisms to protect the integrity of remote access sessions.
        • STIG Viewer - Application Security and Development: V-222534 - Service-Oriented Applications handling non-releasable data must authenticate endpoint devices via mutual SSL/TLS.
        • STIG Viewer - Application Security and Development: V-222562 - Applications used for non-local maintenance must implement cryptographic mechanisms to protect the integrity of maintenance and diagnostic communications.
        • STIG Viewer - Application Security and Development: V-222563 - Applications used for non-local maintenance must implement cryptographic mechanisms to protect the confidentiality of maintenance and diagnostic communications.
        • STIG Viewer - Application Security and Development: V-222577 - The application must not expose session IDs.
        • STIG Viewer - Application Security and Development: V-222596 - The application must protect the confidentiality and integrity of transmitted information.
        • STIG Viewer - Application Security and Development: V-222597 - The application must implement cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission.
        • STIG Viewer - Application Security and Development: V-222598 - The application must maintain the confidentiality and integrity of information during preparation for transmission.
        • STIG Viewer - Application Security and Development: V-222599 - The application must maintain the confidentiality and integrity of information during reception.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use